Data bundling and fast dormancy based upon intelligent application learning

ABSTRACT

Data bundling and fast dormancy controls are provided based on application monitoring and classification. Moreover, a balance is enabled between saving battery power of a user equipment (UE) and reducing signaling and processing load in a radio resource controller (RRC). For instance, a system can observe data flow related behavior of applications on the UE. On receiving a first data flow request, an arrival time of a next data flow request is predicted based on an analysis of the behavior, and the system determines whether the two data flows can be bundled together and transmitted over a single connection. Additionally, on completion of the first data flow, the arrival time of the next data flow request is predicted based on the analysis, and the system determines whether a fast dormancy timer can be disabled to transmit the next data flow over the current connection.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 15/484,195 (now U.S. Pat. No.9,942,853), filed on Apr. 11, 2017, entitled “DATA BUNDLING AND FASTDORMANCY BASED UPON INTELLIGENT APPLICATION LEARNING”, which is acontinuation of U.S. patent application Ser. No. 14/858,405 (now U.S.Pat. No. 9,655,166), filed on Sep. 18, 2015, entitled “DATA BUNDLING ANDFAST DORMANCY BASED UPON INTELLIGENT APPLICATION LEARNING”, which is acontinuation of U.S. patent application Ser. No. 12/947,188 (now U.S.Pat. No. 9,167,618), filed on Nov. 16, 2010, entitled “DATA BUNDLING ANDFAST DORMANCY BASED UPON INTELLIGENT APPLICATION LEARNING”. Theentireties of the foregoing applications are hereby incorporated byreference herein.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, moreparticularly, to a mechanism that facilitates data bundling and fastdormancy based on intelligent learning and characterization ofapplications employed by a user equipment (UE), to reduce networksignaling in the communication network.

BACKGROUND

Universal Mobile Telecommunications System (UMTS) networks have seen anexplosive data growth in past few years and, in future, are expected tosee continuing growth in the Packet Switched (PS) domain. Beyond datatraffic volume growth, an even more aggressive growth in data signalingload has been detected. Among all the signaling messages/procedures onUMTS networks, Radio Access Network (RAN) signaling procedures havecaused the most growth and impact. This is due to complicated radioresource sharing techniques required to conserve resources occupied byvarious users and services.

The majority of RAN signaling events are for connection setup and statetransitions (e.g., during Channel Switching). Typically, when a datapayload is to be sent from/received by a user equipment (UE), a requestis sent to a radio network controller (RNC) to establish a dedicatedchannel (DCH). Once the data payload is sent or received, multipleinactivity timers are triggered by the RNC and upon expiration of thetimers, the RNC transitions the UE from DCH to forward access channel(FACH) and then to IDLE state. To achieve resource efficiency, suchtimers are often set to short values (cumulatively around 12-16seconds). Thus, the UE is quickly moved into the IDLE state aftercompletion of a current data session (download and/or upload). Sincethere is no active data connection between the UE and the core networkduring the IDLE state, power consumption is minimized. Data applicationson the UE initiate multiple data payloads for communication between theUE and RNC. However, the applications operate independently from theradio network perspective, which leads to requesting and establishingmultiple independent connections for payloads from differentapplications. As a result, even though battery life of the UE isconserved, a large number of signaling events are generated and RNCprocessing load is substantially increased.

In addition to network initiated inactivity-based state transition, UEmanufacturers have introduced a fast dormancy (FD) feature thatinitiates direct transition from DCH to IDLE or FACH to IDLE, before therespective network inactivity timer expires. In this type of systemcontrol, the UE proactively releases the data connection, established bythe RNC, directly from DCH to IDLE or FACH to IDLE as quickly aspossible, to further conserve UE battery life. However, once the UE isin the IDLE state, the data connection must be reestablished tocommunicate another payload. The reestablishment of the data connectionis resource intensive, consumes a high amount of power in the RNC, andcan significantly drive up the RNC load.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates signaling loadoptimization in a communication network.

FIG. 2 illustrates an example system that can be employed for creatingapplication profiles in a user equipment (UE).

FIG. 3 illustrates are example profiles created by observing and/orreceiving information associated with data applications on a UE.

FIG. 4 illustrates an example system that facilitates data bundling andfast dormancy based upon intelligent application learning.

FIG. 5 illustrates an example system that facilitates automating one ormore features in accordance with the subject innovation.

FIG. 6 illustrates an example system that facilitates data bundling andfast dormancy based on user interactivity.

FIG. 7 illustrates an example timeline that depicts when an applicationprofiler (AP) engine can perform data bundling and/or can disable fastdormancy.

FIG. 8 illustrates an example methodology that can be utilized tofacilitate data bundling and fast dormancy based on applicationmonitoring.

FIG. 9 illustrates an example methodology that facilitates data bundlingof data flows from different applications to reduce network signaling.

FIG. 10 illustrates an example methodology that overrides a fastdormancy mechanism based on application learning.

FIG. 11 illustrates a block diagram of a UE suitable for data bundlingand controlling fast dormancy based on application characterization inaccordance with the innovation.

FIG. 12 illustrates a Global System for Mobile Communications(GSM)/General Packet Radio Service (GPRS)/Internet protocol (IP)multimedia network architecture that can employ the disclosedarchitecture.

FIG. 13 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “platform,” “service,” “engine,” or the like are generallyintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software in executionor an entity related to an operational machine with one or more specificfunctionalities. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, a program, and/or a computer. By wayof illustration, both an application running on a controller and thecontroller can be a component. One or more components may reside withina process and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers. Asanother example, an interface can include I/O components as well asassociated processor, application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device or computer-readable storage/communicationsmedia. For example, computer readable storage media can include but arenot limited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disk (CD), digitalversatile disk (DVD) . . . ), smart cards, and flash memory devices(e.g., card, stick, key drive . . . ). Of course, those skilled in theart will recognize many modifications can be made to this configurationwithout departing from the scope or spirit of the various embodiments.

In addition, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,” “mobiledevice,” and similar terminology, refer to a wireless device utilized bya subscriber or user of a wireless communication service to receive orconvey data, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream. The foregoing terms are utilizedinterchangeably in the subject specification and related drawings.Likewise, the terms “access point,” “base station,” “Node B,” “evolvedNode B,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream from a set ofsubscriber stations. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” and the likeare employed interchangeably throughout the subject specification,unless context warrants particular distinction(s) among the terms. Itshould be appreciated that such terms can refer to human entities orautomated components supported through artificial intelligence (e.g., acapacity to make inference based on complex mathematical formalisms),which can provide simulated vision, sound recognition and so forth. Inaddition, the terms “data flow,” “data session,” and the like are alsoemployed interchangeably throughout the subject specification, unlesscontext warrants particular distinction(s) among the terms.

The systems and methods disclosed herein, in one aspect thereof, canfacilitate bundling data sessions and controlling fast dormancy based onlearning and characterization of different applications on a userequipment (UE), through historic data tracking and analysis. As anapplication starts to generate data flows, the system tracks thecharacteristics of the application and builds a histogram for variousapplication characteristics, such as, but not limited to, inter-packetarrival time, frequency of use, packet size, session duration, delaytolerance level etc. Moreover, the system includes an applicationprofiler (AP) engine that can predict arrival time of data flows frommultiple applications (downlink or uplink) based on history building andstatistical analysis of the tracked characteristics. Based on thearrival time, the AP engine can determine if the current data flow canbe delayed and bundled with one or more next data flows, as well asdetermine whether a fast dormancy timer can be delayed on completion ofthe current data flow.

According to an aspect, the system, via enabling data bundling andcontrolling fast dormancy, reduces the number of radio resource control(RRC) connection establishments (as part of data connection setup) andthus minimizes Radio network controller (RNC) processing load and callsetup time (latency). Moreover, the system can bundle closely spaceddata payloads and stack data packets from one or more applications inone single connection. This results in decreased number of signalingevents and reduces RNC processing load. Further, by temporarilydisabling fast dormancy the system can avoid unnecessary and pre-maturedata connection releases (and corresponding new data connection setups).

Another aspect of the disclosed subject matter relates to a method thatcan be employed to facilitate data bundling and fast dormancy based onobserving application behavior in a UE. The method comprises monitoringdata applications installed/downloaded on the UE, and generating anapplication profile for each application. Further, the applicationprofiles can be analyzed and the applications can be categorized, forexample, as “random,” “delay tolerant,” and/or “not delay tolerant,”etc. Furthermore, the method includes identifying an arrival time of anext data flow based on statistical analysis. Moreover, it can bedetermined whether the current data flow can be bundled with the nextdata flow based on the arrival time and/or the categorization. Inaddition, the arrival time can also be employed to determine whether afast dormancy timer can be delayed.

The systems and methods disclosed herein reduce network signaling load,and shorten user perceived latency with minimum loss on battery life ofa user equipment (UE). Moreover, the disclosed systems and methodsperform data bundling and/or fast dormancy based on intelligent learningand characterization of applications on the UE. Specifically, the UEmonitors and profiles application activity and tunes data bundlingand/or fast dormancy techniques accordingly, as explained in detailinfra.

Aspects, features, or advantages of the subject innovation can beexploited in substantially any wireless communication technology; e.g.,Universal Mobile Telecommunications System (UMTS), Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), General Packet RadioService (GPRS), Enhanced GPRS, Third Generation Partnership Project(3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2(3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA),or Zigbee. Additionally, substantially all aspects of the subjectinnovation can be exploited in legacy telecommunication technologies.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates signaling load optimization in a communicationnetwork, according to an aspect of the subject specification. Moreover,system 100 performs data bundling and fast dormancy based on intelligentlearning and characterization of applications by a user equipment (UE)102, to reduce network signaling 104 with a Radio Network Controller(RNC) 106. Typically, the core network 108 can include a UMTS network;however, it can be appreciated that the subject innovation is not solimited and most any communication network can be utilized. The corenetwork 108 can be connected to various backbone networks (not shown)for example, the Internet, Integrated Services Digital Network (ISDN),etc.

Typically, UE 102 can include most any electronic communication devicesuch as, but not limited to, most any consumer electronic device, forexample, a digital media player, a digital photo frame, a digitalcamera, a cellular phone, a personal computer, a personal digitalassistant (PDA), a smart phone, a laptop, a gaming system, etc. Further,UE 102 can also include LTE based devices, such as, but not limited to,most any home or commercial appliance that includes an LTE radio. It canbe appreciated that the UE 102 can be mobile, have limited mobilityand/or be stationary.

Typically, when data is communicated between the UE 102 and the corenetwork 108, the UE 102 sends request to the RNC 106, requestingresources to establish a connection. Once the data payload is sent orreceived, the RNC 106 activates multiple inactivity timers, whichfacilitate channel switching at the UE 102. In one example, uponexpiration of the timers, the UE 102 can transition from dedicatedchannel (DCH) to Forward Access Channel (FACH) to IDLE state.Oftentimes, the inactivity timers are set to short values (e.g.,cumulatively around 12-16 seconds) to achieve resource efficiency. Theshort values enable the UE 102 to quickly move to IDLE state aftercompletion of current data session (download or upload).

In addition to network initiated inactivity-based state transition, theUE 102 can also perform fast dormancy (FD) to initiate direct transitionfrom DCH to IDLE or FACH to IDLE, before network inactivity timerexpires. The FD feature in the UE 102 reduces power consumption in theUE 102, by transitioning the UE 102 to the IDLE mode and releasing theconnection as quickly as possible. In traditional systems, when moredata is expected after the UE 102 releases the connection, theconnection needs to be reestablished, which can significantly increasethe RNC load. However, according to an embodiment of the subject system,UE 102 includes a signaling load optimization component 110 thatidentifies such cases (e.g., when data communication is expected) anddeactivates the FD mechanism and/or performs data bundling for closelyspaced sequential data sessions.

Typically, a user can download and utilize various applications on UE102. These applications operate independently from the radio networkperspective and independently establish different connections with theRNC to communicate data payloads. In one aspect, UE 102 can employsignaling load optimization component 110 to bundle closely spaced datapayloads. Moreover, the signaling load optimization component 110 canensure that small data packets are stacked together and sent in a singleconnection, rather than individually via multiple connections. As aresult, substantial amount of signaling can be reduced and the RNCprocessing load can be decreased significantly.

The UE 102 can further include an Application Profiler (AP) component112, which can generate profiles for applications on the UE 102. The APcomponent 112 can monitor activity and track characteristics associatedwith each application that generates an outgoing data flow requestand/or receives an incoming data flow request from the network 108.Moreover, the AP component 112 can predict if and/or when a new dataflow request will be initiated by observing data flow relatedcharacteristics of the applications, forecasting trends and/oridentifying probabilities for the new data flow request. Based on theprediction, the signaling load optimization component 110 can determinewhether to bundle data payloads from one or more applications and sendthe bundled data payloads as one data transmission. Further, thesignaling load optimization component 110 can identify whether fastdormancy can be disabled/delayed at the end of a given data flowtransmission (e.g., due to a prediction that a new data flow requestwill be initiated shortly).

Real network study has shown that the RNC processor load related tochannel switching and data connection setup, e.g., radio resourcecontrol (RRC)/radio access bearer (RAB) setup, together can be as highas 70% of the total RNC processor load. Further, study shows that RRCconnection establishment (as part of data connection setup) involvesmultiple signaling handshake messages, not only increasing RNCprocessing load but also increasing prolong call setup time (latency).Conventional systems employ static state transition timers at RNC level,for all UEs served by the RNC, regardless of the UE type, applicationsrunning on these UEs and/or User interactions/awareness of theseapplications. In contrast, system 100 provides UEs (e.g., UE 102) thatcan intelligently bundle delay-tolerant data to reduce signaling loadand disable/delay FD for situations with high likelihood of close spaceddata sessions to reduce signaling load, as well as shorten call setuptime. In addition, system 100 can also improve performance and extendbattery life of UE 102. Typically, when a new bearer/connection is setup by the UE 102, a ramp-up interval occurs initially, whereinconservative and inefficient attributes produce sub-optimal performancefor some time at the beginning of a data flow. With bundling, the numberof bearer activations are reduced and proportionally less time is spentin ramp-up; thus leading to improved performance and battery life of UE102.

Referring to FIG. 2, there illustrated is an example system 200 that canbe employed for creating application profiles in a UE 102 in accordancewith an aspect of the subject disclosure. It can be appreciated that theUE 102 and the AP component 112 can include functionality, as more fullydescribed herein, for example, with regard to system 100. As discussedsupra, in one example, the UE 102 can be connected to the mobile corenetwork through a wireless radio access network, such as, but notlimited to UMTS Terrestrial Radio Access Network (UTRAN). Moreover, theUE 102 can include most any mobile and/or stationary, wireless and/orwired, electronic communication device (e.g., cell phone, PDA, tablet,PC, laptop, etc.).

Application(s) 202 can include most any computer program(s), function(s)and/or instruction(s) to perform an activity, action, and/or taskassociated with UE 102. Typically, application(s) 202 can bepre-installed on UE 102 during manufacture, downloaded by customers fromapp stores and/or other mobile software distribution platforms, and/orprovided by a service provider on service activation or at most anyother time. Moreover, application(s) 202 can include data application(s)related to various fields, such as, but not limited to, business,entertainment, finance, games, health and fitness, maps and navigation,music or radio, news and weather, productivity, ringtones, wallpapers,skins and themes, social networking, sports and recreation, travel,utilities, etc. For example, application(s) 202 can include anapplication that enables users to surf the Internet, blog, access socialnetworking websites, listen to radio stations, and/or play simple tocomplex games. In another example, a location application can determinea location of the user, a friend or provide turn-by-turn instruction fornavigation. In yet another example, a medical application can be used torecord/track a user's vital signs (e.g., heart rate) over a period oftime and send them to a doctor for review.

In one aspect, monitoring component 204 can tack data flows associatedwith each application 202. In particular, monitoring component 204 canidentify characteristics of the application(s) 202 and performstatistical analysis, for example, build a histogram, for variousfeatures associated with an application, such as, but not limited to,inter-packet arrival time, frequency of use, packet size, sessionduration, delay tolerance level etc. In one example, when an applicationis installed and/or downloaded, information associated with thecharacteristics of the application can be received by the monitoringcomponent 204 from the application itself, and/or queried by themonitoring component 204 from another entity, for example, a networkserver or web server. In another example, monitoring component 204 canmonitor, track and/or record behavior (e.g., inter-packet arrival time,frequency of use, packet size, session duration, delay tolerance leveletc.) associated with an application over a period of time.

Further, the AP component 112 can include a profile creation component206 that can analyze data monitored by monitoring component 204 togenerate a profile for each application(s) 202. Moreover, a profile caninclude one or more profile keys that describe the behavior of theapplication with respect to data flows. Typically, more an applicationis utilized, more accurate the learning (e.g., by monitoring component204) and profiling (e.g., by profile creation component 206) for suchapplication will be. In one aspect, the by monitoring component 204 andprofile creation component 206 can concurrently track, learn and buildprofiles for all applications that generate an outgoing data flowrequest and receive a incoming data flow request from network. Theprofile creation component 206 can store the profiles in an applicationprofile database 208. Moreover, on learning or monitoring (e.g., bymonitoring component 204) new information associated with anapplication, the profile creation component 206 can update and/or modifythe application's profile stored in the application profile database208. Further, profile creation component 206 can delete a profileassociated with an application from the application profile database208, if the application is deleted or uninstalled.

Additionally, the profile creation component 206 can employ most anymachine learning/artificial intelligence technique and develop astatistically satisfactory prediction module for a set of applications202. A set of applications can be marked as random due to theirrandomness of data flows, and will not be included in final decision foroptimization of signaling load. In one example, UE 102 can be employedto operate as a mobile hotspot and can communicate with one or moretethered devices. In this example scenario, data flows to/from thetethered devices can also be marked as “random” and generally notincluded to identify whether data bundling is to be performed and/or FDis to be delayed.

Typically, the application profile database 208 can include volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can include read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasablePROM (EEPROM), or flash memory. Volatile memory can include randomaccess memory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), and direct Rambus RAM (DRRAM). The memory (e.g., data stores,databases, caches) of the subject systems and methods is intended tocomprise, without being limited to, these and any other suitable typesof memory.

Referring now to FIG. 3, there illustrated are example profiles 300created by observing and/or receiving data associated with applicationson a UE, according to an aspect of the subject disclosure. Typically,profiles 302 _(1-N) can be created/updated by profile creation component206 and stored in application profile database 208, which are more fullydescribed herein, for example, with regard to system 200. It can beappreciated that most any number “N” of application profilescorresponding to applications on the UE can be created and stored (whereN is a natural number from one to infinity). Further, it can beappreciated that although nine profile keys (304-320) are depicted ineach profile of FIG. 3, the profiles 302 _(1-N) can include greater orfewer number of profile keys.

In one aspect, a profile key (304-320) can be most any parameter orcharacteristic of an application with respect to data sessions/flows toand/or from the communication network. As an example, Inter-arrival time(I) 304 can be measured by observing the interval between one data flowrequest and the next data flow request, associated with an application(e.g., the data flow request can be initiated by the application or thenetwork). Typically, the last interval, the last X number of intervals(e.g., X is most any natural number), average of the intervals, etc. canbe stored in the in the profile. Further, Frequency Use (F) 306 can beindicative of the usage intensity of the application. For example, howoften is the application generating a data flow request, regardless ofthe request being initiated by network or by the UE itself. Furthermore,Packet Size (P) 308 can provide information indicative of the size of apayload sent/received during a data flow. For example, the number ofbytes of payload that are sent/received for each data flow, an averagenumber of bytes of payload are sent/received during data flows, and/ornumber of bytes sent/received based on a type of data flow, etc., can bestored in the profile. Typically, this data can be used to predict whenthe transmission will be completed, if session duration data isincomplete and/or missing.

Additionally or alternately, Session duration (S) 310 can indicate howlong each data flow transmission will last, from a first byte of payloadto a last byte of payload transmission. Further, Delay tolerance (D) 312can indicate whether or not the application can tolerant delay and canalso specify how many seconds of delay it will allow withoutcompromising service quality or user satisfaction. As an example, thedelay tolerance 312 can be determined by measuring how often the userinteracts with the application (e.g., pressing a button related to theapplication, responding to a prompt of the application, having audio orvideo played—which can indicate that the user is listening or viewing,etc.). For instance, web browsing with Web Search Application (App) willlikely be profiled as less delay tolerant app than Social Networking App(when the Social Networking App is not opened by user).

Furthermore, Application Interactivity time (IT) 314 can also be storedwithin a profile 302 _(1-N). Moreover, the Application Interactivitytime indicates how soon after data reception, does the userutilize/interact with the data. For example, if a user typically putsthe pertinent application in the foreground soon after data receptionthen the application can be considered less delay tolerant. In anotherexample, if the user never opens the application within 15 minutes ofincoming data receipt then the application can be considered as delaytolerant (e.g., with 15 second delay). In one aspect, once applications302 _(1-N) have been flagged as delay tolerant, their continued use maybe used to identify an Average Interactivity Time for delay tolerantapplications. Average Interactivity Time for delay tolerant applicationscan be used to identify an optimal bundling interval. For example, if adelay tolerant application is rarely opened within 15 minutes of datareception then the risk of 15-minute bundling intervals is relativelylow.

In yet another aspect, service provider, UE manufacturer and/orapplication creator's/developer's preferences 316 can also be identified(e.g., during provisioning) and stored in a profile 302 _(1-N). Further,the profile 302 _(1-N) can store user preferences 318, defined by auser, for example, a UE owner. In one aspect, the user can define userpreferences 318 during an initial setup phase, for example, when theapplication is installed. However, it can be appreciated that theservice provider, UE manufacturer and/or application creator'spreferences 316 and/or user preferences 306 can be updated, definedand/or deleted at most any time. With the above profile keys 304-320,and the time of the day (T) and date or day of the week (W) 320, theProfile (P) of a given application (e.g., i^(th) application, wherein iis any natural number from one to infinity) can be defined as: Pi=f(Ii,Fi, Pi, Si, Di, T, W). It can be appreciated that the profile can be afunction of a subset of the above listed profile keys and/or can be afunction of most any additional profile keys, which indicate dataemployed to predict optimization of signaling load.

FIG. 4 illustrates an example system 400 that facilitates data bundlingand fast dormancy based upon intelligent application learning, accordingto an aspect of the subject innovation. Specifically, system 400performs intelligent learning and characterization of applications onthe UE 102, to reduce network signaling in the communication network(e.g., UMTS). Application activity is monitored and profiled over timeand data bundling and/or fast dormancy techniques are tuned to suit.Moreover, UE 102, signaling load optimization component 110, APcomponent 112, and the application profile database 208 can includefunctionality, as more fully described herein, for example, with regardto systems 100 and 200.

Typically, the signaling load optimization component 110 can include anAP engine 402 that is utilized to identify whether data flows should bebundled together, and/or whether fast dormancy should be disabled. Inone aspect, the AP engine can analyze profile data (e.g., stored inapplication profile database 208) associated with an application toclassify the application. For example, applications can be classified asrandom, delay tolerant, low delay tolerant, etc. Typically, applicationsclassified as random, e.g., due to their randomness of data flows, arenot included in final decision for data bundling and/or FD. According toan aspect, the AP engine 402 can predict when a new data flow will beinitiated, based on an analysis (e.g., mathematical/statistical) ofprofile data and/or machine learning techniques. Further, the AP engine402 can employ the analysis and/or classification data to determinewhether or not to hold (delay) transmission of a data flow request,based on prediction of when a new data flow request will be initiated(e.g., so they can be bundled together and be sent as one datatransmission). For example, if the AP engine 402 can identify a firstdata flow as delay tolerant and determine that a new data flow will beinitiated shortly. In this example scenario, a data bundling (DB)component 404 can be employed to delay the first data flow and bundlethe first and second data flows. Moreover, the DB component 404 canstore the first data flow request in a bundle cache 408, until thesecond data flow request is initiated/received. If the prediction isincorrect and the second data flow request does not arrive within theexpected delay, the first data flow can be sent/received, for example,on expiration of a bundling timer. Further, the AP engine 402 can alsoidentify whether the fast dormancy mechanism performed by a fastdormancy (FD) component 406 can be disabled at the end of a data flowtransmission (e.g., due to forecast of new data flow request shortly).

According to an embodiment, the AP engine 402 can predict and/orcalculate, for an i^(th) application (wherein i is any natural numberfrom one to infinity), arrival time (Ai) of a next data flow based onthe start time of last data flow (Ai−1) and profile Pi. Thus, Ai=f(Pi,Ai−1). Moreover, the AP engine 402 can simultaneously and/orconcurrently calculate a value ‘A’ for each application active inbackground or foreground, and generate a comprehensive view of apossibility (or likelihood) of concurrence of data flow request frommultiple applications, and/or a possibility (or likelihood) and durationof overlapping of data flow requests from multiple applications. Basedon the foregoing, the AP engine 402 can instruct the DB component 404 towhether or not to delay transmissions (bundle), and/or the FD component406 to hold/disable a FD trigger, which transitions the UE 102 into anIDLE state.

In general, the AP engine 402 does not apply bundling or FD hold for lowdelay tolerant applications. For example, the AP engine 402 can simplygenerate an invalid input (e.g., such as negative infinite number) forPi, so no valid output can be derived for the low delay tolerantapplication, leading to no decision (e.g., the DB component 404 and/orthe FD component 406 can follow default handling: send data flow requestout immediately). It can be appreciated that user input can override theresults generated by the AP engine 402. Moreover, the AP engine canreceive a copy of what a User Interface (UI) function module (not shown)receives and communicate internally at most any time. This can ensureuser perceived latency is kept at the same level as if no bundling is inuse.

FIG. 5 illustrates an example system 500 that employs an artificialintelligence (AI) component 502, which facilitates automating one ormore features in accordance with the subject innovation. It can beappreciated that the UE 102, AP component 112, AP engine 402, DBcomponent 404, and FD component 406 can include respectivefunctionality, as more fully described herein, for example, with regardto systems 100, 200, and 400.

The subject innovation (e.g., in connection with predicting arrivaltime, creating profiles, classifying applications, bundling data flowsor applying FD hold) can employ various AI-based schemes for carryingout various aspects thereof. For example, a process for determiningwhether to delay a data transmission for bundling and/or disable a FDmechanism can be facilitated via an automatic classifier system andprocess. Moreover, the classifier can be employed to determine anarrival time of a next data flow, generate an application profile,classify applications, identify when bundling or FD hold is to beapplied, etc.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a confidence that the input belongs to a class, thatis, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. In the case of communicationsystems, for example, attributes can be information (e.g., profile keys)stored in application profile database 208 and the classes can becategories or areas of interest (e.g., levels of priorities,classification of applications, etc.).

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs, which the hypersurface attempts to split the triggeringcriteria from the non-triggering events. Intuitively, this makes theclassification correct for testing data that is near, but not identicalto training data. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, neural networks, fuzzy logic models, and probabilisticclassification models providing different patterns of independence canbe employed. Classification as used herein also is inclusive ofstatistical regression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject innovation can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing UE behavior, user interaction, applicationbehavior/activity, application characteristics, receiving extrinsicinformation, etc.). For example, SVM's are configured via a learning ortraining phase within a classifier constructor and feature selectionmodule. Thus, the classifier(s) can be used to automatically learn andperform a number of functions, including but not limited to determiningaccording to a predetermined criteria when data flows from multipleapplication can be delayed and bundled together in one transmission,when a FD mechanism can be disabled, how a profile for an applicationcan be populated, how can application can be classified, etc. Thecriteria can include, but is not limited to, historical patterns, UEbehavior, user preferences, application creator preferences, serviceprovider preferences and/or policies, UE device parameters, profilekeys, location of the UE, etc.

FIG. 6 illustrates an example system 600 that facilitates data bundlingand FD based on user interactivity (UI), according to an aspect of thesubject innovation. Moreover, system 600 utilizes multiple userinteraction indicators to identify data sessions with low “userawareness sensitivity” (e.g., user is not actively interactive withdevice) and bundles the identified data sessions together, thus avoidingmultiple single data connections. Further, FD is avoided when high “userawareness sensitivity” is detected; thus avoiding unnecessary and/orpre-mature data connection releases and corresponding new dataconnection setups. It can be appreciated that the UE 102, AP component112, AP engine 402, DB component 404, and FD component 406 can includerespective functionality, as more fully described herein, for example,with regard to systems 100, 200, 400, and 500.

UE 102 can include a UI component 602 that can be employed to monitoruser input and/or data flow requests. Typically, the UI component 602can detect time correlations and/or gaps and provide informationassociated with the UI to the AP engine 402. In addition toclassification based on delay tolerance, the AP engine 402 can alsocategorize and treat each data flow request according to“interactivity”, for example, by considering the user input thatpreceded it. As an example, if a data flow request closely follows userinput it can be considered “interactive”. In another example, if audioor video playback is in progress the associated data application can beconsidered “interactive”. Alternately, if a data flow request does notfollow user input closely or does not include audio or video playback itcan be considered “non-interactive”.

According to an aspect, if a data flow request is initiated more than“X” (wherein X can be most any predefined or dynamically adjustedpositive rational number) seconds after last user input, the large timedistance (X) between user input and the start of the data flow is anindication that the user is not interacting with the device, not waitingfor the data and/or not likely to request anything else soon. In thisexemplary case, the AP engine 402 can instruct the DB component 404 tohold the outgoing data request in a bundle cache (e.g., 408) until abundling timer expires. Typically, the bundling timer can provide afixed and/or dynamic delay, which can be adjusted automaticallyaccording to load measurements. After the bundling timer has expired,the DB component 404 can initiate a data flow, process all bundledrequests together, and terminate the data flow using fast dormancyimmediately after the bundle cache is empty. The bundle cache can alsobe emptied by various other events, such as, but not limited to, a voicecall and/or user input, that trigger data flows to begin before thebundling timer has expired. Some applications shall run in thebackground without requiring user inputs (e.g., internet radioapplication). The AP engine 402 can classify these applications incertain conditions as “high awareness applications” (e.g., Interactive)which will be excluded from bundling.

In addition, based on the interactivity data from the UI component 602,the AP engine 402 can disable FD by the FD component 406. For example,if a user input occurred less than “X” seconds (wherein X can be mostany predefined or dynamically adjusted positive rational number) beforethe data flow request is made; the AP engine 402 can classify this dataflow request as “interactive” and accordingly disable FD.

In one aspect, the DB component 404 can also utilize network radio loadindications, such as, but not limited to, downlink Ec/Io (ratio ofreceived pilot energy, Ec, to total received energy or the total powerspectral density, Io) and/or a current uplink interference level (SIB7),to dynamically determine and/or scale the bundling delay (T_(b)). Forexample, if Ec/Io and/or SIB 7 uplink noise are poor, the value ofbundling timer (T_(b)) can be increased, to reduce additional loadingimpact. However, if Ec/Io and/or SIB 7 uplink noise are optimal, thevalue of bundling timer (T_(b)) can be decreased (e.g., bundling is notperformed, or bundling is performed for a very short interval).

Referring to FIG. 7, there illustrated is an example timeline 700 thatdepicts when the AP engine 402 can perform data bundling and/or candisable fast dormancy. Each bar in FIG. 7 can represent a unique datasession of the different applications (APP1-APP3). Although only threeapplications are illustrated, it can be appreciated that the subjectdisclosure is not so limited and that most any number of applicationscan be employed for data bundling and/or detecting when fast dormancycan be disabled.

In one example, at the end of data flow transmission of the second datasession of APP 2 (at t₀), fast dormancy would be typically triggered byFD component 406. In one aspect, if the AP engine 402 predicts a highlikelihood of a second data session of APP1 coming in within ‘Delay 1’seconds by employing profiling function P( ) and if the fast dormancytimer<delay 1<Sum (DCH_to_FACH timer, FACH_to_IDLE timer), then the APengine 402 can notify the FD component 406 to hold off FD and allow thenetwork timers to continue the state transition process. Accordingly, UEcan avoid re-establishing a new RRC connection for the second datasession of APP1.

In another example, consider a scenario wherein APP1 and APP2 areclassified by the AP engine 402 as “delay tolerant” applications. Whenthe fourth data flow request of APP1 is received (at t₁), the AP engine402 can predict that another data flow request, for example, the fifthdata flow request of APP2 will be initiated within a short delay.Typically, the AP engine 402 can also forecast the amount of delay(e.g., ‘Delay 2’) and notify the DB component 404 to hold off sendingthe fourth data flow request of APP1 and wait for forecasted delay(e.g., ‘Delay 2’). According to one aspect, if the fifth data flowrequest of APP2 is not initiated before ‘Delay 2’ expires, the AP engine402 can notify the DB component 404 to release the hold and allow thefourth data flow request of APP1 to be sent/received. Alternately, whenthe fifth data flow request of APP2 is initiated within the ‘Delay 2’,the DB component 404 can bundle the fourth data flow request of APP1 andthe fifth data flow request of APP2, and transmit the data flowstogether. In another example scenario, wherein APP3 is profiled by theAP engine 402 as “low delay tolerant” and/or “high awareness”application (e.g., such as web browsing application, mappingapplication, gaming application, etc.), a delay will not be applied(e.g., by the DB component 404) for any data flow request to/from APP3.

FIGS. 8-10 illustrate methodologies and/or flow diagrams in accordancewith the disclosed subject matter. For simplicity of explanation, themethodologies are depicted and described as a series of acts. It is tobe understood and appreciated that the subject innovation is not limitedby the acts illustrated and/or by the order of acts, for example actscan occur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device orcomputer-readable storage/communications media.

Referring now to FIG. 8, illustrated is an example methodology 800 thatcan be utilized to facilitate data bundling and FD control, based onapplication learning, according to an aspect of the subject disclosure.Typically, methodology 800 can be performed by a UE, such as, but notlimited to, a cellular phone, a laptop, a tablet, a PC, a PDA, anetbook, a gaming module, a media player, a media recorder, a mediaviewer, etc. Moreover, one or more applications can be utilized by theUE. For example, the applications can be installed on the UE duringmanufacture and/or downloaded/installed at any other time (e.g., by auser, service provider, etc.) from an online app store and/or othersoftware distribution platform.

At 802, the applications, for example installed/downloaded on the UE,can be monitored. Moreover, the characteristics of the applications canbe observed and histograms and/or other statistical/historical dataanalysis tools can be generated for various profile keys associated withthe applications, such as, but not limited to, inter-packet arrivaltime, frequency of use, packet size, session duration, delay tolerancelevel etc. Typically, the more a given application is used, more theapplication activity/behavior can be monitored and more accurate the“learning” and “profiling” for such application will be. At 804, anapplication profile can be created and stored for each application.According to an aspect, the application profile includes the profilekeys identified for the application.

Further, at 806, the application profiles can be analyzed. Furthermore,at 808, the applications can be classified based on the analysis. Forexample, the applications can be classified as “random,” “delaytolerant,” and/or “not delay tolerant.” In addition, at 810, the arrivaltime of a next data flow can be predicted based on the analysis. At 812,it can be determined whether the current data flow can be bundled withthe next data flow. In an aspect, the classification of the current dataflow can be utilized for the determination. For example, if the currentdata flow is “random,” and/or “not delay tolerant,” it can be determinedthat bundling cannot be performed. However, if the current data flow is“delay tolerant” it can be determined that bundling can be performed.Accordingly, if determined that bundling can be performed, then at 814,data bundling can be performed, based on the prediction and/orclassification.

Typically, after the current data flow is completed, at 816, it can bedetermined whether the next data flow is expected to arrive within ashort delay. As an example, the short delay value can be predefinedand/or dynamically adjusted and can typically lie between the FD timerexpiration value and the sum of the T_(DCH) _(_) _(to) _(_) _(FACH) andT_(FACH) _(_) _(to) _(_) _(IDLE) timer expiration values. If the nextdata flow is expected to arrive within the short delay, then at 818, FDcan be disabled. Alternately, if the next data flow is not expected toarrive within the short delay, then at 820, FD is enabled and canoperate normally.

FIG. 9 illustrates an example methodology 900 that facilitates databundling of data flows from different applications to reduce networksignaling in accordance with an aspect of the subject specification. UEsenable users to download and utilize multiple data applications in thesame device, but each application operates independently from thecommunication network perspective. Methodology 900 provides automatedintelligence to bundle closely spaced data payloads from differentapplications, such that, data packets from different applications can bestacked and sent in one single connection, instead of sending each datapacket individually over different connections. As a result, the amountof signaling events can be substantially reduced, leading to a decreasein RNC processing load.

At 902, a first data flow request associated with an application isreceived. At 904, an arrival time of a second data flow request can bedetermined. It can be appreciated that the second data flow request canbe initiated by the same application or a disparate application.Moreover, the arrival time of the second data flow request can bepredicted based on an analysis of profile data associated with theapplications. Typically, profile data can include historical informationand/or application/UE behavior characteristics relating to data flows.In addition the profile data can also be employed to classify (e.g.,random, delay tolerant, not delay tolerant, etc.) the applicationassociated with the first data flow request.

According to an embodiment, at 906, it can be determined whether theapplication associated with the first data flow request is delaytolerant, for example, based on the classification. If determined thatthe application is not delay tolerant, then at 908, the first data flowcan be sent/received without data bundling. In contrast, if determinedthat the application is delay tolerant, then at 910, the first data flowrequest can be sent to (and stored within) a bundle cache. Moreover, at912, it can be identified whether the second data flow request has beenreceived. At 914, the first and second data flows can be sent/receivedtogether, if the second data flow request has been received. If not, at916, it can be determined whether a bundle timer T_(b) has expired. IfT_(b) has not expired, the methodology can wait for the second data flowrequest, as shown at 912, else, if T_(b) has expired, the first dataflow can be sent/received, as shown at 908. It can be appreciated thatalthough methodology 900 illustrates an example scenario wherein twodata flow requests can be bundled, it can be appreciated that thesubject disclosure is not so limited, and that most any number of dataflow requests can be bundled together.

FIG. 10 illustrates an example methodology 1000 that overrides a FDmechanism based on application learning, according to an aspect of thesubject innovation. Moreover, methodology 1000 employs historical andstatistical based prediction, to determine whether FD can be temporarilydelayed to reduce signaling load. Specifically, by temporarilydelaying/disabling FD, unnecessary and pre-mature data connectionreleases (and corresponding new data connection setups) can beprevented, resulting in reduced signaling load on RNC and improved userperceived latency.

At 1002, completion of a first data flow can be detected. Typically,once the data flow is completed, multiple inactivity timers (T_(DCH)_(_) _(to) _(_) _(FACH), T_(FACH) _(_) _(to) _(_) _(IDLE)) are initiatedby the RNC, upon expiration of which the UE transitions from DCH_to_FACHand FACH to IDLE state. In addition, the UE can initiate a FD timer(T_(FD)) to initiate direct transition from DCH to IDLE or FACH to IDLE,before the network inactivity timers expire. At 1004, an arrival time(T_(x)) of a second data flow request can be predicted. For example,application behavior can be monitored and/or tracked to generate profilekeys, which can be analyzed to facilitate the prediction. At 1006, itcan be determine whether the second data flow request is likely toarrive after the expiration of the FD timer (T_(FD)), but before theexpiration of the network inactivity timers(T_(DCH) _(_) _(to) _(_)_(FACH), or T_(FACH) _(_) _(to) _(_) _(IDLE)). In one example, a highlikelihood can be obtained by comparing a calculated probability valueto a threshold. If the probability is lower than the threshold, thelikelihood can be determined as low likelihood; else, it can bedetermined as high likelihood. Accordingly, if T_(FD)<T_(X)<(T_(DCH)_(_) _(to) _(_) _(FACH)+T_(FACH) _(_) _(to) _(_) _(IDLE)), then at 1008,FD can be disabled (or delayed). However, if T_(FD)<T_(X)<(T_(DCH) _(_)_(to) _(_) _(FACH)+T_(FACH) _(_) _(to) _(_) _(IDLE)) does not hold true,then at 1010, FD can be triggered to transition the UE to IDLE state.

Referring now to FIG. 11, there is illustrated a block diagram of a UE1100 suitable for reducing RNC load, based on application profiling, inaccordance with the innovation. The UE 1100 can include a processor 1102for controlling all onboard operations and processes. A memory 1104 caninterface to the processor 1102 for storage of data and one or moreapplications 1106 (e.g., applications 202) being executed by theprocessor 1102. A communications component 1108 can interface to theprocessor 1102 to facilitate wired/wireless communication with externalsystems (e.g., femtocell and macro cell). The communications component1108 interfaces to a location component 1109 (e.g., GPS transceiver)that can facilitate location detection of the UE 1100. Note that thelocation component 1109 can also be included as part of thecommunications component 1108.

The UE 1100 can include a display 1110 for displaying content downloadedand/or for displaying text information related to operating and usingthe device features. A serial I/O interface 1112 is provided incommunication with the processor 1102 to facilitate serial communication(e.g., USB, and/or IEEE 1394) via a hardwire connection. Audiocapabilities are provided with an audio I/O component 1114, which caninclude a speaker for the output of audio signals related to, forexample, recorded data or telephony voice data, and a microphone forinputting voice signals for recording and/or telephone conversations.

The device 1100 can include a slot interface 1116 for accommodating asubscriber identity module (SIM) 1118. Firmware 1120 is also provided tostore and provide to the processor 1102 startup and operational data.The UE 1100 can also include an image capture component 1122 such as acamera and/or a video decoder 1124 for decoding encoded multimediacontent. The UE 1100 can also include a power source 1126 in the form ofbatteries, which power source 1126 interfaces to an external powersystem or charging equipment via a power I/O component 1128. Inaddition, the UE 1100 can be substantially similar to and includefunctionality associated with UE 102 described supra. Moreover, UE 1100can include a signaling load optimization component 110, AP component112, DB component 404, and FD component 406, which can includerespective functionality, as more fully described herein, for example,with regard to systems 100, 200, and 400-600.

Now turning to FIG. 12, such figure depicts an example GSM/GPRS/IPmultimedia network architecture 1200 that can employ the disclosedcommunication architecture. In particular, the GSM/GPRS/IP multimedianetwork architecture 1200 includes a GSM core network 1201, a GPRSnetwork 1230 and an IP multimedia network 1238. The GSM core network1201 includes a Mobile Station (MS) 1202, at least one Base TransceiverStation (BTS) 1204 and a Base Station Controller (BSC) 1206. The MS 1202is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber identity Module (SIM). The SIM includes an InternationalMobile Subscriber Identity (IMSI), which is a unique identifier of asubscriber. The MS 1202 includes an embedded client 1202 a that receivesand processes messages received by the MS 1202. The embedded client 1202a can be implemented in JAVA and is discuss more fully below. It can beappreciated that MS 1202 can be substantially similar to UE 102 andinclude functionality described with respect to UE 102 in systems 100,200, and 400-600.

The embedded client 1202 a communicates with an application 1202 b(e.g., application(s) 202) that provides services and/or information toan end user. Additionally or alternately, the MS 1202 and a device 1202c can be enabled to communicate via a short-range wireless communicationlink, such as BLUETOOTH®. As one of ordinary skill in the art wouldrecognize, there can be an endless number of devices 1202 c that use theSIM within the MS 1202 to provide services, information, data, audio,video, etc. to end users.

The BTS 1204 is physical equipment, such as a radio tower, that enablesa radio interface to communicate with the MS 1202. Each BTS can servemore than one MS. The BSC 1206 manages radio resources, including theBTS. The BSC 1206 can be connected to several BTSs. The BSC and BTScomponents, in combination, are generally referred to as a base station(BSS) or radio access network (RAN) 1203.

The GSM core network 1201 also includes a Mobile Switching Center (MSC)1208, a Gateway Mobile Switching Center (GMSC) 1210, a Home LocationRegister (HLR) 1212, Visitor Location Register (VLR) 1214, anAuthentication Center (AuC) 1218, and an Equipment Identity Register(EIR) 1218. The MSC 1208 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1210 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1220. In other words, the GMSC 1210 providesinterworking functionality with external networks.

The HLR 1212 is a database or component(s) that comprises administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. The HLR 1212 also includes the current location of each MS. TheVLR 1214 is a database or component(s) that contains selectedadministrative information from the HLR 1212. The VLR containsinformation necessary for call control and provision of subscribedservices for each MS currently located in a geographical area controlledby the VLR. The HLR 1212 and the VLR 1214, together with the MSC 1208,provide the call routing and roaming capabilities of GSM. The AuC 1216provides the parameters needed for authentication and encryptionfunctions. Such parameters allow verification of a subscriber'sidentity. The EIR 1218 stores security-sensitive information about themobile equipment.

A Short Message Service Center (SMSC) 1209 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1202. A PushProxy Gateway (PPG) 1211 is used to “push” (e.g., send without asynchronous request) content to the MS 1202. The PPG 1211 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1202. A Short Message Peer to Peer (SMPP) protocol router 1213is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. It is often used toallow third parties, e.g., content suppliers such as news organizations,to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1202 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1204 and the BSC 1206.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location-updating events occur.

The GPRS network 1230 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1232, a cell broadcast and a GatewayGPRS support node (GGSN) 1234. The SGSN 1232 is at the same hierarchicallevel as the MSC 1208 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1202. The SGSN also keepstrack of individual MS's locations, security functions, and accesscontrols.

A Cell Broadcast Center (CBC) 1233 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1234 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1236. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1236, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN. In a GSM/GPRS network, GPRS services and GSMservices can be used in parallel. A GPRS network 1230 can be designed tooperate in three network operation modes (NOM1, NOM2 and NOM3). Anetwork operation mode of a GPRS network is indicated by a parameter insystem information messages transmitted within a cell. The systeminformation messages dictates a MS where to listen for paging messagesand how signal towards the network. The network operation moderepresents the capabilities of the GPRS network.

The IP multimedia network 1238 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1240 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1240 are a call/session control function (CSCF),a media gateway control function (MGCF) 1246, a media gateway (MGW)1248, and a master subscriber database, called a home subscriber server(HSS) 1250. The HSS 1250 can be common to the GSM network 1201, the GPRSnetwork 1230 as well as the IP multimedia network 1238.

The IP multimedia system 1240 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1243, a proxy CSCF (P-CSCF) 1242, and a serving CSCF (S-CSCF) 1244. TheP-CSCF 1242 is the MS's first point of contact with the IMS 1240. TheP-CSCF 1242 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1242 can also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1243 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1243 can contact asubscriber location function (SLF) 1245 to determine which HSS 1250 touse for the particular subscriber, if multiple HSS's 1250 are present.The S-CSCF 1244 performs the session control services for the MS 1202.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1244 alsodecides whether an application server (AS) 1252 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1250 (or other sources, such as an application server 1252). TheAS 1252 also communicates to a location server 1256 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1202. The MME 1258 providesauthentication of a user by interacting with the HSS 1250 in LTEnetworks.

The HSS 1250 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1250, a subscriber location function providesinformation on the HSS 1250 that contains the profile of a givensubscriber.

The MGCF 1246 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1240 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1248 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1248 alsocommunicates with a PSTN network 1254 for TDM trunks. In addition, theMGCF 1246 communicates with the PSTN network 1254 for SS7 links.

Referring now to FIG. 13, there is illustrated a block diagram of acomputer operable to execute the disclosed communication architecture.In order to provide additional context for various aspects of thesubject specification, FIG. 13 and the following discussion are intendedto provide a brief, general description of a suitable computingenvironment 1300 in which the various aspects of the specification canbe implemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 13, the example environment 1300 forimplementing various aspects of the specification includes a computer1302, the computer 1302 including a processing unit 1304, a systemmemory 1306 and a system bus 1308. The system bus 1308 couples systemcomponents including, but not limited to, the system memory 1306 to theprocessing unit 1304. The processing unit 1304 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures can also be employed as the processingunit 1304.

The system bus 1308 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1306includes read-only memory (ROM) 1310 and random access memory (RAM)1312. A basic input/output system (BIOS) is stored in a non-volatilememory 1310 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1302, such as during startup. The RAM 1312 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1302 further includes an internal hard disk drive (HDD)1314 (e.g., EIDE, SATA), which internal hard disk drive 1314 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1316, (e.g., to read from or write to aremovable diskette 1318) and an optical disk drive 1320, (e.g., readinga CD-ROM disk 1322 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1314, magnetic diskdrive 1316 and optical disk drive 1320 can be connected to the systembus 1308 by a hard disk drive interface 1324, a magnetic disk driveinterface 1326 and an optical drive interface 1328, respectively. Theinterface 1324 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1302, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to a HDD, a removable magnetic diskette, and a removableoptical media such as a CD or DVD, it should be appreciated by thoseskilled in the art that other types of storage media which are readableby a computer, such as zip drives, magnetic cassettes, flash memorycards, cartridges, and the like, can also be used in the exampleoperating environment, and further, that any such storage media cancontain computer-executable instructions for performing the methods ofthe specification.

A number of program modules can be stored in the drives and RAM 1312,including an operating system 1330, one or more application programs1332, other program modules 1334 and program data 1336. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1312. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1302 throughone or more wired/wireless input devices, e.g., a keyboard 1338 and apointing device, such as a mouse 1340. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1304 through an input deviceinterface 1342 that is coupled to the system bus 1308, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1344 or other type of display device is also connected to thesystem bus 1308 via an interface, such as a video adapter 1346. Inaddition to the monitor 1344, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1302 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1348. The remotecomputer(s) 1348 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1302, although, for purposes of brevity, only a memory/storage device1350 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1352 and/orlarger networks, e.g., a wide area network (WAN) 1354. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1302 isconnected to the local network 1352 through a wired and/or wirelesscommunication network interface or adapter 1356. The adapter 1356 canfacilitate wired or wireless communication to the LAN 1352, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1356.

When used in a WAN networking environment, the computer 1302 can includea modem 1358, or is connected to a communications server on the WAN1354, or has other means for establishing communications over the WAN1354, such as by way of the Internet. The modem 1358, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1308 via the serial port interface 1342. In a networkedenvironment, program modules depicted relative to the computer 1302, orportions thereof, can be stored in the remote memory/storage device1350. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1302 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be appreciated that the memorycomponents, or computer-readable storage media, described herein can beeither volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory. By way of illustration, and notlimitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).

Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: predictingtiming data indicative of an arrival time associated with a first dataflow generated by a first application of a first device; in response todetermining that the arrival time is within a time period between afirst expiration of a first timer implemented by the first device and asecond expiration of a second timer implemented by a second device,delaying the first expiration of the first timer; and in response todetermining that the arrival time is not within the time period,disconnecting a communication link associated with a second data flowgenerated by a second application of the first device.
 2. The system ofclaim 1, wherein the predicting the timing data comprises predicting thetiming data based on application data associated with the secondapplication.
 3. The system of claim 1, wherein the predicting the timingdata comprises predicting the timing data based on characteristic dataindicative of a characteristic of the second application.
 4. The systemof claim 1, wherein the predicting the timing data comprises predictingthe timing data in response to determining that the second data flowsatisfies a defined criterion.
 5. The system of claim 1, wherein thetime period is a first time period, and wherein the operations furthercomprise: predicting the timing data by monitoring data flows associatedwith the second application during a second time period.
 6. The systemof claim 1, wherein the time period is a first time period, and whereinthe operations further comprise: determining profile data indicative ofprofile keys associated with the second application by analyzing dataflows associated with the second application during a second timeperiod.
 7. The system of claim 1, wherein the time period is a firsttime period, and wherein the operations further comprise: determiningprofile data indicative of a profile key associated with packetized datafor data flows associated with the second application by analyzing thedata flows during a second time period.
 8. The system of claim 1,wherein the time period is a first time period, and wherein theoperations further comprise: determining profile data indicative ofprofile keys that comprise usage data associated with the secondapplication by analyzing data flows associated with the secondapplication during a second time period.
 9. The system of claim 1,wherein the timing data is first timing data, wherein the arrival timeis a first arrival time, and wherein the operations further comprise:predicting second timing data indicative of a second arrival timeassociated with a third data flow generated by a third application ofthe first device.
 10. The system of claim 9, wherein the operationsfurther comprise: in response to determining that the second arrivaltime satisfies a defined criterion, combining the second data flow withthe third data flow.
 11. The system of claim 10, wherein the operationsfurther comprise: in response to the determining that the second arrivaltime satisfies the defined criterion, delaying a transmission ofinformation associated with the second data flow until the secondrequest for the third data flow is received.
 12. A method, comprising:determining, by a system comprising a processor, timing data indicativeof timing information for a first data flow associated with a firstapplication of a first device; in response to determining that thetiming data is between a first expiration time of a first timerimplemented by the first device and a second expiration time of a secondtimer implemented by a second device, disabling, by the system, thefirst timer; and in response to determining that the timing data is notbetween the first expiration time and the second expiration time,transitioning, by the system, the first device to a defined state thatfacilitates a disconnection of a connection link for a second data flowassociated with a second application of the first device.
 13. The methodof claim 12, wherein the determining the timing data comprisesdetermining the timing data based on data associated with the secondapplication.
 14. The method of claim 13, further comprising:determining, by the system, usage data indicative of a frequency of useof the data associated with the second application.
 15. The method ofclaim 12, wherein the determining the timing data comprises determiningthe timing data based on profile data indicative of a behavior profilefor the second application.
 16. The method of claim 12, furthercomprising: determining, by the system, payload information indicativeof a packet size of a data packet transmitted during a communicationbetween the first device and a third device.
 17. A non-transitorymachine-readable medium comprising executable instructions that, whenexecuted by a processor, facilitate performance of operations,comprising: determining timing data indicative of an arrival timeassociated with a first transmission of first data associated with afirst application of a first device; in response to determining that thearrival time is between a first expiration of a first timer of the firstdevice and a second expiration of a second timer of a second device,delaying the first expiration of the first timer; and in response todetermining that the arrival time is not between the first expiration ofthe first timer and the second expiration of the second timer,transitioning the first device to an idle state that facilitatesterminating a second transmission of second data associated with asecond application of the first device.
 18. The non-transitorymachine-readable medium of claim 17, wherein the determining the timingdata comprises determining the timing data based on data associated withthe second application.
 19. The non-transitory machine-readable mediumof claim 17, wherein the determining the timing data comprisesdetermining the timing data based on data associated with the firstdevice.
 20. The non-transitory machine-readable medium of claim 17,wherein the determining the timing data comprises determining the timingdata based on activity data indicative of activities related to thesecond application.